HTTP-based Site-to-Site leaks threads/memory when unable to communicate with remote instance

I am using HTTP-based site-to-site to communicate with a remote instance of NiFi. I am seeing problems communicating, which is okay. But I am seeing CPU load of 600-700 on my system with 32 cores. I am also seeing in a thread dump 10's to 100's threads with the name "I/O dispatcher" and am seeing OOME's. A heap dump shows that the OOME is caused by 64K byte arrays, each being filled with 0's. The byte[] is coming from class org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.