I've been talking with a number of developers who are familiar with the LGLP license, and I have learned a couple of useful things which I thought I would share for anyone who is interested.
The whole point of LGPL is that the user should be able to upgrade the lgpl code/library with different versions. For example, if I were to use JOrbis v0.9 and a user finds that it doesn't work on their system then they should be able to go and fetch JOrbis v1.0 which does work on their system, and use it to play their game with this newer version. It doesn't matter how the user is allowed to be able to do that, as long as it's possible. It is not necessary to dynamically link (although that is often how it is done) - simply releasing the source code for the parts that incorperate JOrbis is sufficient, so the user can rebuild them with a newer version. As long as this basic requirement is met, then it is not necessary to license a project that uses LGPL libraries with the LGPL license.
What is interesting is when you are talking about applets. The basic requirement still stands - that the user must be able to swap out different versions of the LGPL parts. Again, it doesn't matter how the user is allowed to do this, as long as it is possible. For example, you are covered if you provide a link to the source code for whatever parts incorporate the LGPL licensed library (since the user can potentially recompile the source with a different version of the library, create a local html file, and modify the <archive> parameters for the applet to link with the new version). The LGPL license document must also be provided, and if any modifications were made to the original library, those must be clearly outlined and the original source code provided as well. The easiest way would be to bundle all this stuff together in a zip file and provide a link to it somewhere obvious on the website where the applet resides.
One more interesting thing is that you are allowed to modify the source of an LGPL library, so long as you release the modifications back to the community, which could be as simple as posting an archive of the source code for the modified version. The modified source is, of course, still bound by the LGPL.