I believe that the better approach is to look at the application. Why is it creating the lock file? (That's what this sort of thing is called. It's an old UNIX technique for file sharing.) The lock file could be trying to protect a data file. If that is the case then removing the lock file by hand to allow additional instances of the application to access the same shared directory could be a mistake. You could be courting data corruption.
If that is not the case then why was the application designed to create this lock file?
If deleting the lock file is totally harmless then maybe you could configure the application to stop creating the file or to create the file on the client where it is running. Find out if it is using an environment variable to determine the location of the lock file. Maybe you could manipulate that such as defining it readonly to point to a local directory such as $HOME/tmp.
# FILE: .bashrc
You may be able to do something similar with whatever environment variable this application uses, if any.
If the location of the lock file is hard coded into the application then this approach won't work. In that case I would again suggest that you consider whether this lock file may be doing something useful. If the lock file is not doing anything useful then the application designer made a strange decision.