Figured it out: There was another instance of the receiver queue that I did not know about, and SQL Server was load balancing between the instances.