Without a trace it would be a bit hard to find out what's going on.
I can offer you 2 alternatives:
a) Switch the NSS order (query files first, then AD)
This will make sure that the NSS layer checks the local accounts first, if the app is looking for a local account, these results should come first. You can modify the /etc/nsswitch.conf, restart your app and see the results.
by default the file looks like this:
passwd: centrifydc files shadow: centrifydc files group: centrifydc files
you could flip it to look like this:
passwd: files centrifydc shadow: files centrifydc group: files centrifydc
Note: after a few hours, we'll restore this file back to the original configuration. If you get good results and want to keep it like this, you have to modify the adclient.autoedit.nss parameter and set it to false.
b) Rule-out Centrify all together.
You could, leave the domain (disables Centrify) and check how things run with the application.
The command to leave properly is adleave --remove --user [authorized.ad.user]
authorized.ad.user is an AD user that can remove the computer object in the domain.
Once Centrify is out of the picture, you can measure the performance.
Ultimately you need to know what you app is doing. Perhaps other volunteers can chime-in.