Tweener takes over stack and errors after an onComplete

[GoogleCodeExporter]

The try catch at line 859 in tweener.as results in loss of debugger 
functionality in IDE's like flash develop. Errors are outputted by tweener in 
the trace log instead of being caught by the debugger. This is significantly 
less effective than allowing the debugger to do it's job. At the very least it 
should be throwing errors not just sending a trace. 

It also seems to take possession of the stack after the onComplete function.

Original issue reported on code.google.com by fbte...@cubedonline.com on 6 May 2014 at 8:13