This issue only exists in the list-memory-leak-fix branch. I see that it was merged into master, but the files that jsFiddle point to are the latest release files.
While this isn't a "small" file, you can run this to see the issue.
When run against the leak fix, you will see that after clicking "destroy", the Player.store that "RYANBRAUN" is still in the store. If you comment out the line self.on(), you will see that after clicking "destroy" the store is empty.
If you run this against a branch not containing the fix, clicking "destroy" empties the store even with self.on() not commented out.
Thoughts?