Debug technique for debugging an unusual memory leak

Question

I have a windows application (legacy) that leaks a lot of memory. It does not leak private bytes, I only see with process explorer that it keeps loading from time to time many instances of the same (topically) windows dll-s.

Is there a tool I can use to "trap" the moments when dll-s are being mapped to the process space so that I can track that (with the application symbols) to the source code ?