Support View of this situation:
The path /opt/csw indicates use of Blastwave. The reason for using Blastwave in preference over native Solaris tools is more up-to-date patches and more easily managed with "apt equivalent” method of installs, apt being the native Debian packager. Note it appears Blastwave rolled up in 2012 and they have been replaced with OpenCSW. See the OpenCSW web site for more information.
There are additional indications that using the OpenCSW version of SSH which will respect a lot of paths for things such as LD_LIBRARY_PATH as opposed to the native Solaris SSH stack, which doesn't.
What has been done to resolve this is technically correct to ensure the OpenCSW versions of libraries take priority over others we provide. The assumption here is that our version of Apache will work properly with newer zlib compression libraries provided through OpenCSW. This may technically work but is technically unsupported. It may work but is unsupported due to lack of formal testing to provide support on this use case.
This is the risk with using OpenCSW as a layer over native Solaris. This is similar to use of CentOS instead of RHEL and the related policy around use of non-standard Linux variants. It is technically possible but RHEL is the tested and supported platform.
In this situation it is wonderful that the solution is working for both eHealth and SSH functionality. Though we do have to note that if this change does impact other product areas, if it is proven as the cause for those issues, we will request and require a change back to default.