That is server side.

It's also a dead issue - cause wasn't technically a leak but a combo of memory constrained servers and nodejs's garbage collector not kicking in before it was too late.