Memory leak in the MongoDB .NET driver.

Our team has noticed some memory issues in our application. We have been performing some memory profiling tests and have noticed that after a large query the BsonChunkPool object will stay around without being GC. 

I've created a sample app to demonstrate the issue. Once you run the app, use the seed data button, and then fetch the data. If you have a memory profiler running you should see that the BsonChunkPool is not deleted. https://github.com/Beastw00d/MongoWebApp

We have been using dotMemory as our memory profiler. I've attached an image of the profiler from the demo app. The BsonChunkPool takes up 7.88 MB (top right of image). In our real app it takes 35 MB and up.