I don't know much about specific Patterns for J2ME
However, I am familiar with things that would lead to patterns.
For instance, we know that the memory for a mobile
unit is small, and therefore try to limit what is done on the client, but also really limit all the calls to outside help. If you are continually calling a web server or other server for services, the traffic really slows things down.
So what that leads to is using things like Proxy, Adapter, and Facade patterns on the client side, and Coarse designs on the server side. Coarse meaning instead of three calls to get three data pieces from the server, it can be done in one call to the server that returns a Collection or Text of all the data returned in from the one call.
Obviously, my statements are on the higher level thought process of design, and applications require specific ways of implementation, but keeping those thoughts will keep things cleaner for you.
Hope that helps, and that I am not completely off course in my advice.
But I am sure if I am that someone else will clear it up.
Mark