New feature: getting a stack trace on leaked objects with VTK_DEBUG_LEAKS

Not sure to see how it is related to my suggestion.

In any case, valgrind do not catch vtk leaks has the memory is released when closing.