Improved handling of children removal from empty DisplayObjectContainers

Calling removeChildren() on an already empty DisplayObjectContainer should not fail with out of range error, but do nothing (as the container is already empty) and return an empty array of removed elements for consistency.
Merge pull request #859 from n1313/patch-1

Improved handling of children removal from empty DisplayObjectContainers