Take a look at the txredisapi library. Its a quite complete twisted implementation of both individual connection and connection pools (persistent and non-persistent) for redis.
I've been using for a twisted project for a few months now and I've been quite happy with it.
Wait, ok maybe I missing what your trying to ask.
When I look at your code I see some odd things, like it looks like your spawning up a connection to redis on data receive from your telnet, that won't just create a connection per telnet, that will create a connection per data-flush on that telnet connection (This is almost certainly not what you want it to do).
Take a look at the examples with txredisapi they are more detailed then the examples I see with txredis
Roughly speaking what needs to happen is your logic should be split in two, one part should get the redis connection(s) live and the other part (which is basically what you have now) should process the telnet connections and push commands over the redis connection(s). The txredisapi lib will do all the redis work for you (... and txRedis may too, I don't know that lib well enough to know, the the txredisapi examples should help you either way).
(This style of question has come a a lot in the last few days, you might find a previous answer helpful to understand a common separation between parts in twisted, see: Persistent connection in twisted)