tempdb utilization is a function of the application, in your case application was developed in a way where it does heavy use of features that end up hitting tempdb.
Question for you... is this intense utilization of tempdb creating an I/O bottleneck?
In the affirmative case. A way to improve performance in regards to tempdb is to spread it in as many datafiles -located in different disks - as processors you got in the server. The rationale behind this strategy is that SQL Server would manage work load across all these datafiles then minimizing the chances of seeing I/O bottleneck.
Pablo (Paul) Berzukov
Author of Understanding Database Administration
available at Amazon and other bookstores.Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.