This is a well-known issue that we shouldn't still be discussing in 2011. Any sane JavaScript implementation already addresses this issue, and any responsible JavaScript framework will address this issue for you for the sake of older browsers (e.g. see the jQuery source at https://github.com/jquery/jquery/blob/master/src/event.js#L1...).
To say that we all do this is more than a bit of an exaggeration.
It's definitely a stretch to say we all run into these issues, but you'd be surprised how many beginner and intermediate-level developers don't know about this issue precisely because they've been insulated from it by frameworks.
There are plenty of situations where developers can find themselves dealing with insane JavaScript implementations and irresponsible JavaScript frameworks. While the article doesn't explain exactly what the issue is and which browsers it affects (leading me to believe the author himself doesn't truly understand these memory leaks), the recommendation given is a sound one.
> It's definitely a stretch to say we all run into these issues, but you'd be surprised how many beginner and intermediate-level developers don't know about this issue precisely because they've been insulated from it by frameworks.
To say that we all do this is more than a bit of an exaggeration.