Fixes bug with resource leak

[bmourat]

Fixes bug with resource leak crash in a strict mode. A bug can be reproduced with the following code

try {
   for(int i = 0; i < 100; i++){
     Log.d("CYCLE", "i = " + i );
     MetricsManager.trackEvent("Closeable leak");
     Thread.sleep(750 + (long)(Math.random() * 1250));
   }
 } catch (InterruptedException e) {
      e.printStackTrace();
 }

It seems like the problem is not calling disconnect method after the connection is used.

[ElektrojungeAtWork]

Isn't this problematic?!
send() opens the connection and then, it gets disconnected() right away? Shouldn't we do this once we received the response?

[bmourat]

It is not problematic, we already got the response since send is synchronous.

[ElektrojungeAtWork]

Ok