I often find that I want to push multiple web projects to a given set of servers.

If I'm doing this 'by hand', I have to navigate to the project property pane, change the server, and then do the 
un/deploy action for each project.

if I'm working on code that has a number of such projects that all have to essentially be released together, this 
process becomes tiresome and error prone fairly quickly.

eg: 

suppose there are 4 'environments' that need to be published to on a regular basis.

local
dev
test
prod

I have 3 projects:

projA
projB
projC

for the 'local' setup, all projects point to my local installation of glassfish.
for the 'dev' setup, projA and projB publish to 'serverA', but projC publishes to 'serverB'
for the 'test' setup, projA->server1, projB->server2, projC->server3
for the 'prod' setup, projA->server10, projB->server11, projC->server12

this would

a) be a huge time saver
b) provide consistency across multi developer projects
c) help reduce error by omission or mistake

further, the projects may have dependancies which mean that the projects should be pushed in a particular sequence, so 
that would need to be factored into the solution also.

open-esb based BPEL projects should be included in the list of project types that can be organised into this solution.