Added session destruction functionality

Well a lot of moving parts.

It turns out the request.session (from express-connect) and redis are somehow decoupled. 

Have a nice weekend :)
We need to handle an error here - what can it be? Is the information compromising to the server? We need to define a constant error message for every erroneous case.