Beginnings of connection pooling configuration.
Applied @Skamander's recommendations for the connection pool size and fixed up the locator for the Akka dispatcher (we need to fix our Play doc on this subject).

I have observed that the thread pool executor is now being used with the correct number of threads.
No need to generate a parallel range - will just add to the elapsed time as generating 10 futures is a short lived operation and doesn't require parallelism.
Resolving the ec just once now.
Aligned cp size with some of the other projects being benched.
The Java version now submits futures to the dbEc execution context
Merge pull request #96 from huntc/connection-pooling

Beginnings of connection pooling configuration.