Fixed AdminServiceBasicTest which had wrong slop pusher job definition
Updated Protobuff to 2.3
Remove protobuf 2.2.0
Added Entropy Detection
Fixed a 'leaking sockets' issue wherein the client was creating more sockets than specified by the configuration.

The root cause was that when connection or protocol negotiation requests in ClientRequestExecutorFactory timed out, we weren't closing the socket before throwing the error. Because the sockets are handled asynchronously, the socket would eventually connect and then be abandoned. Nonetheless, the socket was taking up a thread on the server (using the thread-per-connection socket store implementation). On node bannage (and subsequent pool recycling) this lead to a large number of these "zombie" sockets which left "live" sockets with no available threads on the server.
Added more unit tests to pusher job + Slop key generation
Modified unit test to do out of order delivery of slops
Don't claim (in the logs) that application errors are fatal
Implemented asynchronous hinted handoff to reduce latency
Converted StreamingSlopPusherTest to JUnit4
Decreased the default Admin connection timeout to 30 seconds
Added a utility to stress test the client
Clean up stress test code
Clean up code, minimize test transiency
Consistent naming and indentation for ec2 targets
Support starting a cluster on ec2 without deploying to all nodes
Added 'early termination' to Streaming slop pusher job
Reduce verbosity for access logs in LoggingStore
Update CONTRIBUTORS
Set curr.release to 0.90.RC1