Fix for #296

Twemproxy handles this internally - we were incorrectly blocking it.

StackExchange.Redis/StackExchange/Redis/ConnectionMultiplexer.cs

@@ -1758,8 +1758,6 @@ private WriteResult TryPushMessageToBridge<T>(Message message, ResultProcessor<T
                 switch (server.ServerType)
                 {
                     case ServerType.Cluster:
-                    case ServerType.Twemproxy: // strictly speaking twemproxy uses a different hashing algo, but the hash-tag behavior is
-                                               // the same, so this does a pretty good job of spotting illegal commands before sending them
                         if (message.GetHashSlot(ServerSelectionStrategy) == ServerSelectionStrategy.MultipleSlots)
                         {
                             throw ExceptionFactory.MultiSlot(IncludeDetailInExceptions, message);