pntdevops-vvasilev discovered a bug in our .postinstall script that is damaging Solaris environments by overwriting ld's /var/ld/ld.config.

When you run crle with "-l" you need to specify the original paths as well. Otherwise it will replace them.
Here is from the man page:

-l dir

Specify a new default search directory dir for ELF objects. Multi-
ple occurrences of this option are permitted.

The default search paths for 32-bit ELF objects are /lib followed
by /usr/lib. For 64-bit ELF objects, the default search paths are
/lib/64 followed by /usr/lib/64.

Use of this option replaces the default search path. Therefore, a
-l option is normally required to specify the original system
default in relation to any new paths that are being applied. How-
ever, if the -u option is in effect, and a configuration file does
not exist, the system defaults are added to the new configuration
file. These defaults are added before the new paths specified with
the -l option.

I don't find this issue being a Blocker, because our JWS 3.0.3 httpd postinstall also contains just:

276 if [ ".$SUGID" = ".root" ]
277 then
278     if [ -x /usr/bin/crle ]
279     then
280         /usr/bin/crle -u -64 -l $INSTALL_ROOT/lib64
281     fi
282 else
283     echo "WARNING: Not a superuser. Solaris runtime linker environment \`crle' was not updated." >&2
284 fi