Err: Max Connections

I'm running into a max connections error when running on Heroku: `ERR max number of clients reached`

When I do a `client list` in Redis I see a ton of connections that look like this:

```
id=28 addr=23.20.17.18:59295 fd=33 name= age=14 idle=14 flags=b db=0 sub=0 psub=0 multi=-1 qbuf=114 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=blpop
id=29 addr=23.20.17.18:59296 fd=34 name= age=14 idle=14 flags=b db=0 sub=0 psub=0 multi=-1 qbuf=450 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=blpop
id=30 addr=23.20.17.18:59302 fd=35 name= age=14 idle=14 flags=b db=0 sub=0 psub=0 multi=-1 qbuf=477 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=blpop
id=31 addr=23.20.17.18:59298 fd=36 name= age=14 idle=14 flags=b db=0 sub=0 psub=0 multi=-1 qbuf=188 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=blpop
id=32 addr=23.20.17.18:59297 fd=37 name= age=14 idle=14 flags=b db=0 sub=0 psub=0 multi=-1 qbuf=188 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=blpop`
```

- How many connections does Kue.js normally need to create?
- Are the number of connections directly related to how many job types I'm creating/processing?
- If i have 10 different job types, does that mean I need 10 different connections to listen for each type?

The issue names no files or tests. Start by inspecting Kue's Redis connection handling and compare it with the Heroku Redis client list, focusing on the blocked blpop clients. Done means establishing how many connections Kue creates, whether job types affect that count, and documenting an actionable answer.

Written by the indexing model from the issue text.