Find and debug memory leaks with callbacks

[garretraziel]

It's likely that Qubie contains a lot of memory leaks. It seems that every "temporary callback" should be cleaned up properly at the end (when connection closes etc.), but this definitely isn't the case in bc11n. It looks like that when code binds callback function to a socket, this callback should be cleared when socked is closed. Go through the code, find all callbacks and examine whether they should be cleared.

[garretraziel]

See this article for help: http://blog.flowdock.com/2015/06/22/debugging-node-js-memory-leaks/