Failed Deployment creating locks?

System

We see a new lock on an adjacent file when a deployment fails because a file is locked. So after the first failure, there are 2 locked files. After the next, 3 - and so on.

1) Could there be a bug in OD 6.1.1 causing this?
2) Can OD be told to ignore locks, especially if it's the task holding the lock? I see the 4 parms rmReadOnly, svrTryCount, svrTryInterval, and scrTryDisableOverwrite. I'm not quite sure what the 4th does, but the first 2 don't help if the file's locked and the third deals with read-only, not locked, files. Is there another parm that might help?
3) Is there an easy way to find all locked files (Windows Server 2003)?

Thanks in advance,
Peter Buck