Yes that's not surprising, the code for that implementation is quite scary and in order to make the page not lag terribly I realized at the end that I would eff

Yes that's not surprising, the code for that implementation is quite scary and in order to make the page not lag terribly I realized at the end that I would effectively have to re-invent some of what react.js does (because it would have taken too long to completely re-write). I've considered re-writing an open source version with react that people could fork and incorporate into course material, but all that stuff takes time. I can think of a few places where there would probably be circular object references, so that's probably where the memory leaks come from. Thanks for the feedback :)