AnimationSequence objects may incorrectly share state

[cris@…]

Creating two distinct animation sequences then running one concatenates the sequences, where they should stay separate.

Fix is to add a line to the AnimationSequence? constructor:

this._anims = [];

The prototype defines an empty array, but the instances share it except in the case where one calls removeAll. This line gives the instance its own array of animations.

[alex]

(In [2800]) fixes #321

[(none)]

Milestone 0.2.2release deleted