Calling .remove on a set of matched elements they are indeed removed from the DOM, but IE8 keeps internal references to them, leaking memory.

This is probably due to a bug in IE8 implementation of removeChild. Adding the a call to ''removeNode'' does seem to remove the leak.

node.removeNode(false);

To reproduce, copy the fiddle at http://jsfiddle.net/H3jQc/ to a local file and run it through sIEve on a computer with IE8 installed. Each time the ''Test'' button is clicked, one SPAN element is leaked.

The problem does not show in IE9 or later. jQuery versions from at least 1.7.2 to the latest 1.10.x seem to be affected.