Reading between the lines, I think this may be a case of focusing on the wrong issue. The real issue is not the presence or absence of the lock files. They are a result of the real issue, and until you address that problem, deleting, or trying to delete, lock files won't help.
At the risk of retracing old ground, let's review deployment.
Access applications need to be split into the interface (forms, reports, queries and code) and the data storage (tables only).
The interface, called a Front End, is an accdb. Each user has their own, exclusive, copy of that accdb. It is better to deploy each user's copy of the Front End, or FE, on each user's computer, although, as Gasman pointed out, a shared network drive location can work if it's set up adequately.
The data accdb, called a Back End, is deployed into a network folder. All copies of the FE accdbs link to the tables in that shared Back End, or BE. And that's where you "locking file" problem comes into the picture.
Because the BE is shared with one or more users simultaneously, there has to be a mechanism to keep track of all of those simultaneous users. The laccdb, or locking file, controls and tracks all of those users. Access creates it, modifies it, and deletes it. Not you nor your users. Only Access is supposed to manage the locking file. So finding that you need to manually delete it is a symptom of some other problem, and that's what you have to resolve.
One of the key features of this system is that all users must have sufficient permissions on the folder where the BE is located. This is under the control of IT. IT must allow each user to create new files (i.e. the locking file that is created when the first user starts Access and opens the BE). Each user must also have sufficient permissions to make changes to files (i.e. they have to be able to add records inside the accdb, update or delete them inside the accdb.) And each user must have sufficient permissions to delete files (i.e. the locking file).
Again, Access manages the locking file on behalf of users, but the users must also have sufficient rights for Access to make the required actions.
Hanging locking files can be a result of one or more users not having adequate permissions on the folder to perform all of those actions. If something goes terribly wrong, it is possible that a locking file can be left hanging, but under normal operations, you'll never need to intervene.