Configuration source may revert to HTTP (port 8091) during excessive errors

In AWS, I am running this command:
cbc-pillowfight -U couchbase://ec2-54-176-251-0.us-west-1.compute.amazonaws.com/event_stream -t 128 -B 10000 -I 10000 -m 1024 -M 1024 -n -c -1

I am observing many:
Operation(s) failed: [0x17] Client-Side timeout exceeded for operation. Inspect network conditions or increase the timeout

I assume this is related to resource exhaustion and is not the main focus of this bug...but I think it is related so I included it.

The main concern is that within a few seconds of running this command, I observe a large increase in the number of 8091 connections to my Couchbase Server cluster. With the exact command above, the increase is in the range of 60-80 connections before I terminate the command. When adding a "-v" to capture logs, it's only around 6-10 connections increase, but is still more than I would expect and hopefully representative of the problem. With "-vv or -vvv" I am unable to reproduce the behavior which I assume is due to some race condition/context switching.

Logs are here: http://customers.couchbase.com.s3.amazonaws.com/perry/libcouchbase (sorry, it's rather big, the increase of connections should be relatively near the end)