You can indirectly find the JAVA classes that your application loads.
>> [a1,b1,c1] = inmem;
>> run your application
>> [a2,b2,c2] = inmem;
>> setdiff(c2,c1)
c1 and c2 lists the JAVA classes loaded in MATLAB. c2 - c1 will list the extra JAVA classes loaded by your application. The common ones in c1,c2 were most likely loaded by MATLAB and you don't have to worry about them as some of these are not required when you run your compiled application and some are already included with the compiled application.
Note that the issue related to compiling serial function was very specific where the correct .jar files were not picked up during compilation. For the most part, you won't have to do detective work on which .jar files have to be added to the classpath so that the compiled application runs fine. This will be done automatically if the .jar file is shipped with MATLAB.
That being said, the issue with serial command will be resolved soon.
