Windows Non-Interactive Logons (aka Scheduled Tasks) and AFS

Is anyone going to be upset if I disable integrated logon support for
non-interactive logon sessions such as those produced by "Scheduled Tasks"?

It has been brought to my attention that for each non-interactive logon
session a new Kerberos v5 credential cache server is being spawned.  As
a result, some systems that provide large numbers of remote process
executions are falling over when the maximum number of processes is reached.

I have committed code to disable integrated logon support until such
time as I can figure out how to ensure that when the executed process
terminates that the Kerberos v5 credential cache server is terminated.

Thanks.

Jeffrey Altman