Just checking if there has been any movement on this. I have the same problem running a clustered Node app using newrelic 1.14.5 and Node 0.10.28.
Conditionally requiring the newrelic module only for workers in the cluster as suggested in Node.js Agent Memory Leak did not work for me. The only thing that does seem to alleviate the problem is disabling SSL as suggested in Node.js Agent Memory Leak.
I also have heap dumps confirming that there are a number of slabBuffers stemming from https connections not getting GC’ed when SSL is on. Let me know if this might help you find a solution to the problem.
On a related note, have you looked into merging https://github.com/newrelic/yakaa/pull/2 for the keep alive agent? I have stepped through the code and confirmed that the author of the PR is right, there is no property named ‘destroyed’ in the socket object in Node versions <= 0.10.28. The property to check for is named ‘_destroyed’. This does not have any effect in the memory issue with SSL though.