Joost recently wrote (in Memory leak )

"Devel::LeakTrace or one of the other Devel::Leak* modules might help."

WARNING: I have no competence here, but found several threads re Memory Leak, while trying to discover if your "reduced" code was effectively parallel to that which was the subject of yet another discussion (which I have NOT re-found).
HTH