File Descriptor leak in JavaHttpClientTransport

[cdj-offside]

Noticed in one of my services that memory was growing constantly and would eventually reach OOM. Eventually found that it was a socket FD leak, not 100% sure why (I don't know enough about Java's client implementation), but replacing it with an Apache client transport resolved the issue.

This is version 0.0.3, not sure if it's been fixed since then, but just wanted to call it out.

[mtdowling]

Can you check to see if #916 addresses this, and if not, share more about how and what you're calling? Is a payload being sent from the client, is the service returning a payload? Are you consuming it entirely?