Add proper worker thread naming capabilities following recommendations from trustin below:

<galderz> the funny thing that I'm yet to investigate is that we created a ThreadFactory to give a name to the threads but the worker threads used by Netty always look like: "New I/O server worker #"
<trustin> galderz: manik asked the same question about the thread name - You can change that behavior using ThreadRenamingRunnable.setThreadNameDeterminer()
<galderz> so, the thread factory in the executor is ignored then?
<trustin> not ignored but the thread name is set afterwards
<manik> trustin: yes, we've had this discussion before.
<galderz> thx trustin, i'll add a jira to fix that
<galderz> one final thing,
<galderz> one thing I've spotted is that when a clients disconnect
<trustin> (overriden that is)