If you add these lines to the POJO example, you should get a nice stack trace...

try
{
java.beans.Introspector.getBeanInfo(pojo.getClass());
}
catch(Exception e)
{
e.printStackTrace();
}

from an assist.NotFoundException that starts with:
javassist.NotFoundException: mil.army.perscom.ASBS.aop.POJOBeanInfo

It appears that calling
Introspector.getBeanInfo(pojo.getClass()); generates the mil.army.perscom.ASBS.aop.POJOBeanInfo class on the fly. Then Javassist can't find a matching a class file. Is there any way to get rid of the big stack trace?

I'm writing this because you get the same thing when you use Log4j with property file configuration.

Steve Reich