When a user specifies a limit on a find operation, and that limit is reached on the initial batch returned from OP_QUERY, the driver immediately attempts to kill the cursor via OP_KILL_CURSOR after reading the initial batch. The problem is that it does so by pulling another connection from the pool before the connection that was used for the OP_QUERY has been released back to the pool. This effectively doubles the number of connections required for find operations that specify a limit, and in the worst case can cause starvation, where all threads are waiting for connections but none are available.