FULL PRODUCT VERSION :
java version "1.8.0_92"
Java(TM) SE Runtime Environment (build 1.8.0_92-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode)

ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows 7 64 bits [version 6.1.7601] with JDK 1.8.0_91 64 bits
Fedora 23 Linux 4.4.8-300.fc23.x86_64 with Oracle JDK 1.8.0_92 64 bits

A DESCRIPTION OF THE PROBLEM :
When launching the same application with dependencies via Java Web Start, it's start slower with 1.8.0_91(and _92) that 1.8.0_77.
With update 91, Java Web Start try to load all dependencies specified in Class-Path entry of the manifest.mf.
For example, my application needs orb-connector-4.1.jar but in the manifest.mf of this JAR, they are a lots of dependencies in Class-Path.
Before update 91, those entries aren't parsed by java web start.

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Launch an application with dependencies like (glassfish 4.1 client libs) appclient-connector-4.1.jar, orb-connector-4.1.jar, ... that contains a manifest with Class-Path entries


EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
The application starts after a long time in update 91 but starts correctly with java before update 91.

REPRODUCIBILITY :
This bug can be reproduced always.