The other parts, like Session and Entity EJBs, JMS, Java Server Pages, SOAP, SAR and WAR packaging formats, JNDI etc. etc., have long ago been supplanted by much better technologies.
Why servlets instead of Jetty handlers?
As far as Jetty handlers, they might be a good alternative to servlets. I admit I'm not familiar with the details.
I'm coming at this from a lens of "I'm tired of getting laid off all the damn time". Java seems to still be going strong economically/job-availability-wise despite its faults/criticisms after all these years, may as well get on the bandwagon for a 9-5 so I don't get laid off every so often and have to re-skill with the latest new shiny to win "flavor of the month" all the time.
Haven't decided this is THE one and only "one true path" or anything, just exploring it and wondering if this is even viable coming from where I'm at right now. To answer that question, I'd have to know how to get from where I am to where I want to be.
Java is manageable compared to C++, but a big nasty beast compared to Python, Ruby, Go, etc.
I think even in a down economy, a CS education is a good investment of your time. These days you can even do it online, and getting grounded in the fundamentals is a superpower when properly leveraged.