v4 can't quit you - async client usage leaving idle connections?

Maybe I don't understand async/await correctly but can someone help or verify the way to createClient and send commands with async/await that ensures connections actually quit so that all these idle connections aren't made on a recurring script run?

I updated this code from v3 to v4.0.4 and keep getting increasing open(but idle?!) connections that won't go away. (it's on heroku redis if that matters)

near top of module createClient to be used later as a pool connection:

const rclient = require("redis").createClient({
	url: process.env.REDIS_TLS_URL,
	socket: {
		tls: true,
		rejectUnauthorized: false
	},
	legacyMode: true
});
rclient.on('error', (err) => {});

Then later on run a basic SETNX....

  (async () => {
	  try {
		await rclient.connect();
		await rclient.SETNX(...,function(err, dne) {
			if (err) {
				console.log('SETNX problem: '+err);
			} else if (dne) {
				//stuff											
			}
		});
		await rclient.quit();
	} catch (e) {
		console.error(e);
        }
  })();

I include that await quit() there and expect it to close the connection after command completes..... but I keep getting mounting idle connections? (Why don't they just clear out after expiry time?) I just want to send my command and quit! Any direction or verification that this is the correct usage appreciated

Start with the v4.0.4 async client lifecycle around createClient(), connect(), SETNX(), and quit(); no files or tests are named in the report. Determine how the callback-based command interacts with await and how recurring scripts should close the client; done means the connection behavior is verified and documented.