Another possibility is that there is additional programming being run that causes the delay. The GUI (visual interface) may be exactly the same, but you could have five methods called (because of MU or whatever) where there was only one method before.
One way to assess the possibility of a memory leak (without actually using a stack analyzer to watch program memory activity) is to take note under the task manager of the program running memory right before you do a script in this case. Then do the script and compare the numbers. If the memory grows each time (on the local machine or the server) then a memory leak is possible. The script may be entered into a memory array for good reason, but prat of the issue is the additional memory consumed comparable to the info in the transaction [script]. If it is larger than that, then something is being allocated memory that probably shouldn't remain.
We could go with the classic software developer defense - it's not a bug , it's a feature! It is giving you extra time to talk to the patient, rest your typing hands (ala repetitive stress), or to finish the chart in your mind since the machine won't let you chart right then.
Take your pick.
