BinaryShardedJedis.disconnect() may occur memory leak

Scenario:
When the middle node of cluster goes down, BinaryShardedJedis.disconnect() will unable to release connections of the following nodes, this causes memory leak.

Solution:
Ignore the exception node, so that all other normal nodes can release all connections.

This pull request adds a unit test for this solution.
Thanks to @marcosnils's guide.
Isn't this the same as doing:

```java
try {
  jedis.quit();
  jedis.disconnect();
} catch (Exception e) {
  //ignore exception
}

Also, why do we need to catch a generic exception?. When `quit` or `disconnect` fails, doesn't jedis throw a JedisConnection exception?. Shouldn't we catch that exception only?