DOM appears to be held in memory in certain conditions with components rather than be destroyed

[imjoshdean]

I'm still struggling to come up with an easy way to succinctly describe this one. In short I have the following example:

http://jsbin.com/qiziqedage/1/edit?js,console,output

Flattened out, it looks something like this:

{{#if show}}
<layout>
    {{#if state.inner}}
        <internal></internal>
    {{/if}}
</layout>
{{/if}}

where show is a boolean compute and state.inner is a can.Map inside of a can.Map.

If I were to set show to false and remove inner from state, events trigger on internal, specifically in this case removed. If I were to set show to true, add inner back to state, and repeat the process, events trigger on internal twice, again, in this case removed. Inspecting this.element and working your way up the parent tree, you'll find that in all cases except one, the element is attached to a detached layout element.

Not even sure where to begin with this one, but I'll get a test and pull request ready.