I'm not sure if these were causing problems or what problems they would have been causing, but its not good to go around implicitly defining globals.
Implicit globals, creating a possible memory leak. Not sure if these …
…were in fact cause a problem but as I was looking to extend this class those jumped out at me.
Good find! This probably isn't too worrisome a leak, since max leakage is capped at two objects, but trampling over the global scope is definitely a bad thing.
A glance-over doesn't suggest any issues with this. If it runs and the unit tests pass then I recommend a merge.