Close #142

When someone visits `resque/resque` the route was being intercepted by the admin web interface for Resque that was mounted at `resque/`. This fixes the issue.