Memory leak on disposing Flounder

[tar-viturawong-sociomantic]

To reproduce:

var x, y;
x = document.createElement( 'div' );

// start cycle
y = new Flounder( x, { data : [1,2,3] } )
y.destroy();
// force GC, repeat cycle

Result: a leak of 29 DOM nodes and 5 event listeners per cycle (the steps on the right).

[kevin-krug]

@tar-viturawong-sociomantic shouldn't we address this in https://github.com/sociomantic-tsunami/flounder/issues ?

[tar-viturawong-sociomantic]

@kevin-krug-sociomantic I'm not sure whether it's an origin issue or otherwise, actually. Currently, SD master is using Damian's fork, which is where the behavior appears.

[mousemke]

i'm looking at merging damian:master into flounder:dev