Memory Leak, why are there so many ReaderWriterLock objects in my finalization queue?

Question

I have a .NET windows service application with a memory leak.

Overview: The service connects to another service via TCP, and writes data to a SQL server