Make the semantics consistent with Ruby resque workers

Before this commit, the pattern was to register multiple workers for a
given queue, which would cause a job to be sent to each worker once it
came into that queue. Resque actually is designed to work the opposite:
a single worker watches multiple queues. Incidentally, this simplifies
things.