Other comments point out that your proposed solution is probably their problem and they should do a quick ack instead.
Just occurred to me there's a different possibility:
The extra connection bug mentioned could be from a rogue thread/process/code-path connecting to the queue and fetching an item, but somehow not doing the work.
Verifying this likely requires access to the codebase, so treat this as little more than idle speculation.