One of the things about Maven is that it wants to do things its way and if you try to force it to do something different, you are asking for a lot of pain. In Maven, a single POM generates a single primary artifact (yes, you can generate ancillary artifacts, but they are not the main focus of the build - ancillary artifacts are things such as javadoc and source jars). Therefore, Jayesh's advice it the best advice.
If you really want to create a WAR for three JARs in the WEB-INF/lib directory, then create the JARs as separate projects (with their own POMs) and create the WAR in a fourth project (with its own POM) referencing the three JARs as dependencies. I suspect that the classes in 'ui' and 'webservices' reference classes in 'business'; that's OK, just add the dependency to the POMs.
If you cannot do this because the classes cross-reference each other (e.g., 'ui' references 'business' and 'business' references 'ui'), then you should not be placing the classes into separate JARs anyway.
Having said all of that, when I migrated a series of projects from Ant builds to Maven last year, one of the projects generated a primary JAR with all the classes and then a second JAR with only a handful of classes. Considering where that second JAR was later used as a dependency (where it made no sense to include the primary JAR), and considering that some of the classes were generated, I decided that a major refactoring was not feasible. So what I did to add the second JAR as an ancillary artifact was to included a second run of the maven-jar-plugin and I specified and includes list of the files to place in it. You can probably use this mechanism to accomplish your goal. Here is what your plugin definition might look like (I did only two of the jars, you can do the third):
I assume that your POM creates a WAR. If so, the maven-war-plugin runs during the 'package' phase and thus I set the maven-jar-plugin to run in the prior phase.