Things I can find that link to libssl or libcrypto and are closed source:
as-daemon (part of the stuff for talking to Microsoft email servers)
browser.launch (main browser binary)
eapd (WiFi security daemon)
intellisyncd (part of nokia messaging)
libconnui_iapsettings.so.0 (related to WiFi security)
libflashplayer.so (Flash player plugin)
libiap_dialog_gtc_challenge.so (related to WiFi security)
libiap_dialog_mschap_challenge.so (related to WiFi security)
libiap_dialog_private_key_pw.so (related to WiFi security)
libiap_dialog_server_cert.so (related to WiFi security)
libiap_dialog_wps.so (related to WiFi security)
libiap_wizzard_wlan.so (related to WiFi security)
libinternetsettings.so (internet settings control panel)
libshareonovi.so (handles sharing to OVI)
libsync4j.so.3 (syncml stuff)
location-proxy (handles GPS SUPL and network related stuff)
osso-backup.launch (backup tool)
ota-settings (handles internet settings sent over-the-air)
signond (single-sign-on daemon)
syncd (part of maesync, whatever that is)

Identifying which of these binaries call potentially-broken functions (i.e. those who's ABI may have changed between the 0.9.8n we have now and the latest 0.9.8za release) should be possible if someone can come up with a list of all such functions.

Some of these binaries may only use bits of openssl that haven't changed between 0.9.8n and 0.9.8za (e.g. crypto stuff like AES or SHA or HMAC) and some may be things we dont need anymore (e.g. nokiamessaging). Some may link to the libraries but not actually import any functions from them.