As a heads up, you may want to check out the new gem I created called Backburner which is a more modern way to manage asynchronous jobs with beanstalkd in ruby. It follows a cleaner, resque-esque interface, has a truly asynchronous worker (that uses forking and multiple threads for much faster throughput) and has much better error handling and retry support. I was using stalker for 2 years before writing backburner because I wanted a better solution.
It gives you support for things like:
SomeObject.async(:pri => 1000, :delay => 2).some_method(1, 2, 3)
with the method then being automatically enqueued onto beanstalkd and processed asynchronously by backburner workers.