SecureCRT 6.2 Beta 3 - Key Manager Performance Regression?

[Killing]

Since upgrading from 6.0 to 6.2 Beta 3 I've been seeing issue here with some of our rollout scripts.

These scripts use extensive use of ssh agent forwarding in a parallel manor so can be request 20+ key request per second.

The problem exhibits its self by instead of authenticating the onward connection like it should our scripts are prompting to passwords, as though the agent request failed when it shouldn't. Repeating the request to just that machine in a none parallel manor always succeeds so its not a problem with the keys itself.

The SecureCRT upgrade is the only change in the environment I wondering if the key manager has been changed in anyway which could be causing the issues we are seeing.

P.S. Loving the memory footprint improvements in 6.2 80Mb vs 800Mb makes a world of difference