I'm seeing leaks from several tests:

CronetUrlRequestTest.testUnexpectedReads
CronetUrlRequestTest.testUploadReadFailAsync
CronetUrlRequestTest.testUnexpectedFollowRedirects 

They look like this:

07-20 04:57:57.107  6669  6678 E StrictMode: A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.
07-20 04:57:57.107  6669  6678 E StrictMode: java.lang.Throwable: Explicit termination method 'close' not called
07-20 04:57:57.107  6669  6678 E StrictMode: 	at dalvik.system.CloseGuard.open(CloseGuard.java:180)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at java.net.AbstractPlainSocketImpl.create(AbstractPlainSocketImpl.java:103)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at java.net.Socket.createImpl(Socket.java:451)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at java.net.Socket.getImpl(Socket.java:517)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at java.net.Socket.setSoTimeout(Socket.java:1108)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at com.android.okhttp.Connection.connectSocket(Connection.java:195)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at com.android.okhttp.Connection.connect(Connection.java:172)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at com.android.okhttp.Connection.connectAndSetOwner(Connection.java:367)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at com.android.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:130)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:329)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:246)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:457)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:126)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at org.chromium.net.impl.JavaUrlRequest$7.run(JavaUrlRequest.java:696)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at org.chromium.net.impl.JavaUrlRequest$8.run(JavaUrlRequest.java:708)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at org.chromium.net.impl.JavaUrlRequest$SerializingExecutor$1.run(JavaUrlRequest.java:142)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at org.chromium.net.impl.JavaUrlRequest$1$1.run(JavaUrlRequest.java:205)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at org.chromium.net.impl.JavaCronetEngine$1$1.run(JavaCronetEngine.java:58)
07-20 04:57:57.107  6669  6678 E StrictMode: 	at java.lang.Thread.run(Thread.java:761)

I tried running on a Nexus 6 flashed with Nougat but didn't see the failures.
I used an x86 emulator with Nougat and could see the failures.

I'm not entirely sure what's going on but I see at least one problem:
JavaUrlRequest.SerializingExecutor.runTask() only runs one task and then attempts to post the next task to the underlying executor.  This doesn't work well with ExecutorService.shutdown().  At shutdown time, all tasks in the queue should be executed, but because runTask() posts the next task it gets RejectedExecutionException and so only attempts to run one task.  This can lead to the disconnect() task being rejected, even though it was submitted to the queue prior to initiating shutdown().