you can find very detailed information about Jetty and Apache httpd (from http://wiki.eclipse.org/). i think you should decide what you want from a web server more precisely according to the expectations.
Apache httpd is a HTTP server written in C, that is often used to
front other web services. Jetty is a full functional and optimized
HTTP server and has no need of an apache httpd instance between it and
the internet. However, deployers often want to place an instance of
apache between Jetty and the internet for some of the following
Performance. Apache Httpd does have slightly superior performance to jetty for pure HTTP request handling. However, for dynamic response
generation, apache must pass the request to another process and the
resulting double handling reduces the total throughput to less than
direct requests to Jetty. More over, with the advent of comet style
web applications, long held requests are common and the apache thread
model assigns a thread per outstanding request, so apache does not
scale to large numbers of comet connections.
Static content. Apache Httpd is very good at serving static content fast. However, Jetty is no slouch either as it can use direct
memory mapped buffers for static content, so that only kernel space is
used for the data transfer. Besides, if your application has a lot of
static content, then you will get much better results by either
ensuring good client caching or serving the content from an CDNS edge
Security. Some believe that apache gives them a more secure solution as there are no TCP/IP connections terminating on Jetty.
However, since Jetty is written in Java, it is not vulnerable to the
class of security exploit that a server written in C is. Jetty has a
good security record, but has had some past issues, but mostly of the
nature that would not have been helped by a fronting instance of
Load Balancing. Apache has several options for load balancing between multiple servlet servers. These solutions are reasonable, but
there are better software and appliance load balancers available. The
main limitation of apache as a load balancer is that it's threading
model is not-asynchronous, so scaling is limited (specially for comet
Administration. Often an enterprise has staff who are very familiar with apache and thus have a strong preference to deploy
everything behind apache. This can be a good reason to avoid chaos in
a deployment environment, so long as some of the performance and
scalability limitations do not affect your web application.
i hope it helps you...