How can I disable the caching of EJB 3.0 datasources?

I need to find out how to disable the caching of a OC4J application.
We are using Oracle Standalone workflow 9.2.0.8 along with the OC4J 10.1.3.1.0.

The problem is that the modifications by the PL/SQL packages called upon by the workflow, isn't visible inside the EJB 3.0 clients using the OC4J to access the database.
I've been looking on the internet for over a day now, trying to find some suitable solutions.

Right now I'm trying to use a "native data source" in stead of a "managed data source".
I'll keep you posted on the results, and any other methods I can find.

My manager has given me the time to look into this, to make sure we won't use any solutions that wouldn't suit our situation.

Hope someone can help me find a suitable solution.
Kind regards,
Erwin.

After running some more tests and looking up stuff,
I found out that it's actually Oracle Workflow which doesn't commit the needed data on time.

Due to the numerous information and faulty information on the net regarding oracle, I got confused which about case to believe.

Apparently workflow does NOT commit after each activity, and so the needed data created/updated/removed by the PL/SQL methods isn't available yet to the server when the java code is launched.
I think it's strange however that when I restart the application or the entire server, he will pick up the correct data.

Nevertheless, thank you sdstuber for putting your time into this matter.
Best regards,
Erwin.