Fix bug with destroyComponent in a component's destroy method

There was a bug that could cause an uncaught exception when a component's destroy method called `scope.destroyComponent()` on another component.