When using the async API, we have noticed an increase in memory use when executing queries that collect a large amount of documents. A heap dump analysis shows that the connection keeps a reference to a callback, even after it has been called. As the connection itself will be pooled, this may lead to memory "leak" issues, especially when the connection pool is configured to a large maximum size.