Memory leak when tween assigned about easeljs

[danzen]

Hi @DarkMatters - thanks for the report. I wonder if we would want the animation to still be going if we add the child back. When we dispose() in ZIM we recursively go through children and remove animations. But when we remove the child, we do not stop the animations. I do not think there is a dispose in CreateJS so perhaps it is up to the developer to manually remove tweens if they are not going to use them again. I agree, that is tricky to remember and probably does seem like it would be a given. It could be added to the docs at least as an interim solution. Anyone else have any thoughts? Cheers.