At the risk of being pedantic

, it's not Java...it's a series of sun-provided Windows utilities for the JRE...including one that just checks for JRE/plugin updates. You are not running a JVM in the background unless you are trying to run a Java-based application or an applet.
In general, you shouldn't need all that stuff running...even if you want to use Java-based programs. I write client-side Java-based programs for folks for a range of functions...and all that they need is to have a JRE installed on their hard disk somewhere. When they execute a Java-based application, the JVM starts up...and when they exit, it shuts down.
Granted, most Java is now server-side code that provides the back end for Enterprise systems and large web-based systems...and not much client-side code...but there are still a large number of Java-based client apps (e.g., Eclipse and IntelliJ are two that I use every day)...as well as a handful of sites that still use applets. Many Java-based client apps actually come bundled with a JRE. I prefer to distribute without one to keep the size of my install package small. In fact, I don't even need an install package for my apps if the JRE is installed...you can just unzip and run.
Frankly, it's not much different than old school Win 32 MFC or new school .Net-based programs. You need quite a bit installed on your PC for programs created using the frameworks to run...you just tend to already have it with the OS since they are MS technologies.
Of course, being a professional Java developer, perhaps I am being a bit sensitive as well as pedantic.
