May have an answer after some initial digging through Microsoft DEP docos:
"Finally, the Data Execution Prevention message might not be shown for some applications when they encounter a problem with DEP, regardless of the Windows Error Reporting configuration. These applications handle the STATUS_ACCESS_VIOLATION exception raised by DEP, or they install an unhandled exception filter (UEF), which overrides the default Win32 UEF. The default Win32 UEF is responsible for triggering both the Data Execution Prevention and Windows Error Reporting messages. The Data Execution Prevention message may also not be shown if an application has called the SetErrorMode() function with the SEM_NOGPFAULTERRORBOX flag. "
From http://technet.microsoft.com/en-us/library/cc738483.aspx
Possibly, the BD-Java support for some Win32 bluray apps aren't accounting for DEP enabled Win32 environments/systems. So this is an app programming issue.
Good find. Also according to the same article:
"Some application behaviors are expected to be incompatible with DEP. Applications that perform dynamic code generation (such as just-in-time code generation) and that do not explicitly mark generated code with Execute permission might have compatibility problems with DEP. Applications that are not built with SafeSEH must have their exception handlers located in executable memory regions."
My guess is the code for the java menus is being compiled and run on the fly and possibly why this is happening to that one component of BD playback...