odd locking behaviour with smbstatus

[Joel Hammer]

Looking at locked files with smbstatus with 2.2.2 and windows 98 clients,
one running over win4lin.
If a file is opened from a windows client, after the file is closed smbstatus
still shows it as being locked by the windows process. However, another
windows client can access the file without being told it is read only.
Smbstatus obligingly updates itself. Can someone tell me what I am seeing
here and is it of any importance?
I have accepted all the defaults for file locking, which means I am using
oplocks.
Thanks,
Joel