Still on the hunt, seems however that this memory leak occurs as a change somewhere between version 0.3.5 and 0.4.4. I'll try to narrow it down a bit more. Robert