Very interesting problem!
For me the problem only happens in Safari and Safari Mobile (not in Chrome). Is that is the case for you as well?
Additionally, this problem only happens for me when using the back button and then the forward button. If I use the back button and then click the link to the animation again (i.e. no forward button) the problem does not occur. Is that is the case for you as well?
What I found was that when doing a back/forward our jQuery ready function was not called. I thought this was a caching problem and experiemented with tags to disable caching but that didn't help at all.
Then I ran into the article http://stackoverflow.com/questions/158319/cross-browser-onload-event-and-the-back-button which has a great discussion about special back/forward caches in browsers.
in the .js file associated with the Wallaby .html file, or changing the tag in the Wallaby .html to:
The problem you described seems fixed as either one of these modifications ends up disabling the back/forward cache.
We will modify our output to handle this in a future release. In the meantime, users will need to add this themselves.
I'll create a new top level forum topic covering this so that more Wallaby users are likely to find this important information.